Node / meshtastic / Meshtastic-Android / files / docs / uk-rUA / user / settings-module-admin.md

Displaying Rendered • View raw • Download

title: Settings — Modules & Admin

parent: User Guide

nav_order: 8

last_updated: 2026-08-30

description: Configure optional feature modules (MQTT, telemetry, canned messages, TAK, and more) and perform device administration.

aliases:

• modules

• module-config

• administration

Configure optional feature modules and perform device administration. Modules extend Meshtastic with specialized capabilities — each can be independently enabled or disabled.

│ 💡 Tip: You only need to enable the modules you actually use. Disabling unused modules reduces

│ airtime, saves battery, and simplifies your configuration. A module you expect can be missing for

│ three reasons: your node's role does not enable it, your firmware is older than the release that

│ added it, or the firmware build excludes it for this hardware.

Module settings use a card-based layout with toggle switches, dropdowns, text fields, and sliders:

!A toggle setting in the on position

!A dropdown setting, expanded to show its list of options

!A text field setting with a value entered

!A module settings card with its title and grouped controls

Every module lives under Settings → Module configuration.

│ ⚠️ Important: Saving a module screen restarts the radio — the button reads Save & restart, and

│ the radio is unreachable for a few seconds afterwards. External Notification and Mesh Beacon are

│ the exceptions: their button reads Save, and the radio may still restart for some changes.

Bridges mesh messages to and from an MQTT broker for internet connectivity. This is how you extend your mesh beyond radio range or integrate with home automation systems.

Turning Map reporting on reveals a consent card headed _Consent to Share Unencrypted Node Data

via MQTT_, with an I agree. switch under it. The rest of the card does not exist on screen

until you agree:

See MQTT for a detailed usage guide including encryption, privacy, and broker setup.

Enables serial port communication for external device integrations (GPS modules, sensors, or custom hardware). When enabled, the node's serial port can send and receive protobuf or text data, allowing external microcontrollers or computers to interact with the mesh.

Controls buzzer, LED, or vibration alerts on your radio hardware. Useful for devices that need to physically signal when a message arrives — particularly helpful for unattended or outdoor installations.

There are two independent triggers — an incoming message, and a received bell character —

and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.

Buffers messages for nodes that were temporarily offline, then replays them when those nodes reconnect. Essential for meshes where nodes go in and out of range regularly — ensures messages aren't lost during brief disconnections.

│ 💡 Tip: Store and Forward works best on nodes with ample memory (ESP32 with PSRAM). Router nodes

│ are ideal candidates since they're typically always-on.

│ ⚠️ Warning: Range Test only works on a secured primary channel. As long as your primary channel

│ still uses the default channel key, the interval and CSV controls stay disabled — you can still

│ switch an already-enabled module off — and saving force-disables the module if the channel has

│ reverted to public.

Automated range testing tool for evaluating link quality between nodes. When enabled, the node periodically transmits test messages with incrementing counters. A receiver node logs these messages, allowing you to walk or drive away and later analyze at what distance messages stopped arriving.

Controls what telemetry data your node shares with the mesh. Telemetry includes device health (battery, uptime) and environmental sensor data (temperature, humidity, pressure).

Each of the four metric groups has its own enable toggle and its own interval, so you can report

battery health often and sensors rarely.

See Telemetry & Sensors for supported sensors and configuration recommendations.

Pre-configured messages accessible from the radio's physical buttons (for radios with rotary encoders, keypads, or similar input hardware). Define a list of quick-send messages that can be transmitted without a phone connected — ideal for field use.

Codec2 audio support for low-bandwidth voice communication over the mesh. This is an experimental feature that encodes voice into very small data packets using the Codec2 codec.

│ ℹ️ Note: Audio requires specific hardware (I2S microphone and speaker). Voice quality is very

│ low-bandwidth — think "understandable radio voice," not phone-call quality.

GPIO control over the mesh network. Allows a remote node to read or write GPIO pins on another node — useful for activating relays, reading switches, or controlling external hardware from a distance.

│ ⚠️ Warning: Turning on Allow undefined pin access gives remote nodes access to all GPIO pins,

│ which could interfere with the radio's own hardware. Turn it on only on dedicated GPIO nodes.

Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.

See Local Mesh Discovery for how to use neighbor data for mesh topology exploration.

Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. Can be used for visual status indicators, notification lights, or decorative effects.

Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.

People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.

│ 💡 Tip: Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other

│ locations. Counts are approximate — one person may carry multiple devices.

The status message has no module screen. It is edited with the rest of the node's identity, on

Settings — Radio & User.

Broadcasts an invitation to your mesh, and receives invitations from others. The entry appears only

on radios running firmware 2.8.0 or newer. See Local Mesh Discovery for the full

walkthrough.

Team Awareness Kit integration for interoperability with ATAK and WinTAK. Two things have to be

true before the entry appears in the module list: the radio runs firmware 2.8.0 or newer, and its

Device Role on Settings → Device configuration → Device is set to T383838TAK or T383838TAK_TRACKER.

See TAK Integration for detailed setup and usage.

Remotely configure nodes that share your admin key:

1. Select the target node in the node list.

2. Navigate to Settings for that node.

3. Modify configuration.

4. Tap Save — changes are sent over the mesh.

│ ⚠️ Important: Requires an admin key configured on both your node and the target node.

Settings → Administration holds five one-shot actions, each behind a confirmation dialog:

│ ⚠️ Warning: Factory reset erases all settings, channels, and keys, and cannot be undone. Before

│ you reset, use Export configuration to save the radio's settings and Backup Keys on the Security

│ screen to save its keys, so you can put both back afterwards.

Settings → Backup & Restore writes the connected radio's whole configuration to a file with

Export configuration, and reads a saved file back in with Import configuration. Export

before a factory reset, or to copy one radio's setup onto another. The section is shown for your

own radio only, not over remote admin.

Settings → Advanced collects the tools that read or rewrite local state, and is likewise shown

for your own radio only: Firmware Update on OTA-capable hardware, Clean Node Database,

TAK Server, Local Mesh Discovery, and the Debug Panel.

Prunes nodes from your node database — from the app's copy and from the radio's own, so this is

not a display-only cleanup. The two filters combine rather than acting separately; the screen puts

it as Selections are additive.

• Clean up nodes last seen older than N days — always applied. The slider runs from 7 days to

365 and starts at 30; with Clean up only unknown nodes turned on, its floor drops to 0.

• Clean up only unknown nodes — narrows the same purge to nodes that never sent their user

info. The age limit still applies on top of it.

The screen lists the nodes queued for deletion as you move the filters. Clean Now carries the

purge out, after one more confirmation, and it cannot be undone. Favorited nodes, ignored nodes,

and nodes with a public key heard in the last seven days are never removed, whatever the filters

say — that is why the queued list can be shorter than you expect.

Opens the Packets and App logs tabs for viewing, filtering, and exporting diagnostic output. See Debug Logs for the full walkthrough.

Two easy-to-miss entries on the Settings screen configure the app rather than the radio, and

appear only when your own node is selected:

• Node Layout — how much detail each row of the node list shows.

• Message Filter — hides incoming messages that contain words you list. With no words

configured it does nothing.

Settings → About carries the app's own identity rather than the radio's:

Three sections:

• What is Meshtastic? — a short description of the project.

• Apps — opens with Need Hardware?, a rotating carousel of popular devices that links out

to where to buy one. It also lists the GitHub repository, the running app version, and

Acknowledgements (see the next section).

• Project information — links to the website and to this documentation.

Reached from About, this lists every open-source library the app ships, with its license,

generated at build time by AboutLibraries. It was previously called the license screen.

• "No response from target node" — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.

• Changes not applying — some settings require a reboot to take effect. Try the Reboot action after saving.

• Can't see remote settings — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.

• Settings — Radio & User — core radio and user profile settings

• Module configuration reference — detailed module docs on meshtastic.org

• FAQ — common questions on meshtastic.org